Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Github actions #55

Draft
wants to merge 6 commits into
base: master
Choose a base branch
from
Draft

Github actions #55

wants to merge 6 commits into from

Conversation

tizoc
Copy link
Member

@tizoc tizoc commented Mar 28, 2021

  • Test build
  • Produce and publish release binaries

@tizoc tizoc force-pushed the github-actions branch 15 times, most recently from 84da33b to 1fa1062 Compare March 28, 2021 18:19
@tizoc
Copy link
Member Author

tizoc commented Mar 28, 2021

For some reason the tests for the CLisp build fail on Linux, but I am not sure why.

@tizoc tizoc force-pushed the github-actions branch 2 times, most recently from 7821e42 to 2933f9b Compare March 28, 2021 18:36
@tizoc
Copy link
Member Author

tizoc commented Mar 28, 2021

So, the CLisp versions from Ubuntu Groovy, Ubuntu Bionic, and Ubuntu Xenial all behave differently, and the first two are broken. I will disable that for now because I don't have the time or energy to deal with it at the moment.

@tizoc
Copy link
Member Author

tizoc commented Mar 28, 2021

Changelog here from what seems to have changed on CLisp by the Debian maintainers: https://metadata.ftp-master.debian.org/changelogs//main/c/clisp/clisp_2.49.20180218+really2.49.92-3_changelog

@tizoc
Copy link
Member Author

tizoc commented Mar 28, 2021

This fixes the REPL on the version provided by Ubuntu bionic
@rkoeninger
Copy link
Member

Taking CLisp off the default build list is fine I think. SBCL the port, you know.

By the way, CLISP 2.49 (2010-07-07) has always worked for me.

@tizoc
Copy link
Member Author

tizoc commented Mar 30, 2021

@rkoeninger same here, but turns out that newer versions of Ubuntu (and I guess Debian), use updated versions which don't behave the same as 2.49 (and they don't even seem to behave the same between Ubuntu versions).

It is weird that Clisp's latest official release was more than 10 years ago, but I see a bunch of changes up to at least 2018, but no new releases.

Btw, I agree that taking Clisp out from CI is fine (but will probably update the Github Actions script and leave the Makefile with the "all" target as it was). I spent the little time I had this last weekend fighting with those issues and I wasn't able to finish the "release" pipeline, will probably do so this weekend.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants